SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C

C static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C code

  • All rules 315
  • Vulnerability13
  • Bug76
  • Security Hotspot19
  • Code Smell207

  • Quick Fix 19
 
Tags
    Impact
      Clean code attribute
        1. Hard-coded secrets are security-sensitive

           Security Hotspot
        2. "sprintf" should not be used

           Security Hotspot
        3. Changing working directories without verifying the success is security-sensitive

           Security Hotspot
        4. Setting capabilities is security-sensitive

           Security Hotspot
        5. Using "tmpnam", "tmpnam_s" or "tmpnam_r" is security-sensitive

           Security Hotspot
        6. Using "strncpy" or "wcsncpy" is security-sensitive

           Security Hotspot
        7. Using "strncat" or "wcsncat" is security-sensitive

           Security Hotspot
        8. Using "strcat" or "wcscat" is security-sensitive

           Security Hotspot
        9. Using "strlen" or "wcslen" is security-sensitive

           Security Hotspot
        10. Changing directories improperly when using "chroot" is security-sensitive

           Security Hotspot
        11. Using "strcpy" or "wcscpy" is security-sensitive

           Security Hotspot
        12. Using publicly writable directories is security-sensitive

           Security Hotspot
        13. Using clear-text protocols is security-sensitive

           Security Hotspot
        14. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        15. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        16. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        17. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        18. Hard-coded passwords are security-sensitive

           Security Hotspot
        19. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Changing directories improperly when using "chroot" is security-sensitive

        intentionality - logical
        security
        Security Hotspot
        • cwe
        • symbolic-execution

        The purpose of creating a jail, the "virtual root directory" created with chroot-type functions, is to limit access to the file system by isolating the process inside this jail. However, many chroot function implementations don’t modify the current working directory, thus the process has still access to unauthorized resources outside of the "jail".

        Ask Yourself Whether

        • The application changes the working directory before or after running chroot.
        • The application uses a path inside the jail directory as working directory.

        There is a risk if you answered no to any of those questions.

        Recommended Secure Coding Practices

        Change the current working directory to the root directory after switching to a jail directory.

        Sensitive Code Example

        The current directory is not changed with the chdir function before or after the creation of a jail with the chroot function:

        const char* root_dir = "/jail/";
        chroot(root_dir); // Sensitive: no chdir before or after chroot, and missing check of return value
        

        The chroot or chdir operations could fail and the process still have access to unauthorized resources. The return code should be checked:

        const char* root_dir = "/jail/";
        chroot(root_dir); // Sensitive: missing check of the return value
        const char* any_dir = "/any/";
        chdir(any_dir); // Sensitive: missing check of the return value
        

        Compliant Solution

        To correctly isolate the application into a jail, change the current directory with chdir before the chroot and check the return code of both functions:

        const char* root_dir = "/jail/";
        
        if (chdir(root_dir) == -1) {
          exit(-1);
        }
        
        if (chroot(root_dir) == -1) {  // compliant: the current dir is changed to the jail and the results of both functions are checked
          exit(-1);
        }
        

        See

        • OWASP - Top 10 2021 Category A5 - Security Misconfiguration
        • OWASP - Top 10 2017 Category A5 - Broken Access Control
        • CWE - CWE-243 - Creation of chroot Jail Without Changing Working Directory
        • man7.org - chdir
        • man7.org - chroot
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use